-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(frontend): first time choosing a pipeline definition is VERY slow. Fixes #10897 #11130
fix(frontend): first time choosing a pipeline definition is VERY slow. Fixes #10897 #11130
Conversation
Signed-off-by: Elay Aharoni (EXT-Nokia) <[email protected]>
Hi @ElayAharoni. Thanks for your PR. I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
@ElayAharoni: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
please review when you get the chance. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chensun The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…Fixes kubeflow#10897 (kubeflow#11130) Signed-off-by: Elay Aharoni (EXT-Nokia) <[email protected]> Co-authored-by: Elay Aharoni (EXT-Nokia) <[email protected]> Signed-off-by: sefgsefg <[email protected]>
…Fixes kubeflow#10897 (kubeflow#11130) Signed-off-by: Elay Aharoni (EXT-Nokia) <[email protected]> Co-authored-by: Elay Aharoni (EXT-Nokia) <[email protected]> Signed-off-by: sefgsefg <[email protected]>
…Fixes kubeflow#10897 (kubeflow#11130) Signed-off-by: Elay Aharoni (EXT-Nokia) <[email protected]> Co-authored-by: Elay Aharoni (EXT-Nokia) <[email protected]>
…Fixes kubeflow#10897 (kubeflow#11130) Signed-off-by: Elay Aharoni (EXT-Nokia) <[email protected]> Co-authored-by: Elay Aharoni (EXT-Nokia) <[email protected]>
…Fixes kubeflow#10897 (kubeflow#11130) Signed-off-by: Elay Aharoni (EXT-Nokia) <[email protected]> Co-authored-by: Elay Aharoni (EXT-Nokia) <[email protected]> Signed-off-by: zed546213 <[email protected]>
…Fixes kubeflow#10897 (kubeflow#11130) Signed-off-by: Elay Aharoni (EXT-Nokia) <[email protected]> Co-authored-by: Elay Aharoni (EXT-Nokia) <[email protected]> Signed-off-by: chris <[email protected]>
…Fixes kubeflow#10897 (kubeflow#11130) Signed-off-by: Elay Aharoni (EXT-Nokia) <[email protected]> Co-authored-by: Elay Aharoni (EXT-Nokia) <[email protected]>
Fixes #10897.
i found that whenever a V2 pipeline is chosen for a new run, then there is a check whether v1Template is fetching and because it is not a v1 pipeline then the message is seen for long time.
so basically what i did is check whether the v1 template is fetching only when the pipeline is v1 and not v2, which cause in significant reduce in the loading time.